IPLIST.NET - fresco.me
Search for IP or hostnames:
fresco.me checked at 2025-09-13T07:12:43.332Z 808ms 105/105/105 100% R:10
fresco.me
NS | ns-158.awsdns-19.com | ||||||
A | 2600:9000:5300:9e00::1 🇺🇸 Amazon | ||||||
PTR | ns-158.awsdns-19.com | ||||||
A | 205.251.192.158🇺🇸 Amazon | ||||||
PTR | ns-158.awsdns-19.com | ||||||
NS | ns-1020.awsdns-63.net | ||||||
A | 2600:9000:5303:fc00::1 🇺🇸 Amazon | ||||||
PTR | ns-1020.awsdns-63.net | ||||||
A | 205.251.195.252🇺🇸 Amazon | ||||||
PTR | ns-1020.awsdns-63.net | ||||||
NS | ns-1146.awsdns-15.org | ||||||
A | 2600:9000:5304:7a00::1 🇺🇸 Amazon | ||||||
PTR | ns-1146.awsdns-15.org | ||||||
A | 205.251.196.122🇺🇸 Amazon | ||||||
PTR | ns-1146.awsdns-15.org | ||||||
MX | inbound-smtp.us-east-1.amazonaws.com | ||||||
A | 3.211.210.226🇺🇸 Amazon | ||||||
PTR | ec2-3-211-210-226.compute-1.amazonaws.com | ||||||
A | 44.206.9.87🇺🇸 Amazon | ||||||
PTR | ec2-44-206-9-87.compute-1.amazonaws.com | ||||||
A | 44.210.166.32🇺🇸 Amazon | ||||||
PTR | ec2-44-210-166-32.compute-1.amazonaws.com | ||||||
A | 54.164.173.191🇺🇸 Amazon | ||||||
PTR | ec2-54-164-173-191.compute-1.amazonaws.com | ||||||
A | 54.197.5.236🇺🇸 Amazon | ||||||
PTR | ec2-54-197-5-236.compute-1.amazonaws.com | ||||||
NS | ns-1831.awsdns-36.co.uk | ||||||
A | 2600:9000:5307:2700::1 🇺🇸 Amazon | ||||||
PTR | ns-1831.awsdns-36.co.uk | ||||||
A | 205.251.199.39🇺🇸 Amazon | ||||||
PTR | ns-1831.awsdns-36.co.uk |
me
NS | a0.nic.me | ||||||
NS | a2.nic.me | ||||||
NS | b0.nic.me | ||||||
NS | b2.nic.me | ||||||
NS | c0.nic.me |
Up
play-api.fresco.me |
play.fresco.me |
tcssim-api-dev.fresco.me |
office365onboarding.fresco.me |
Starts with same word
Starts similarily
AI analysis
The parent of play-api.fresco.me
, play.fresco.me
, tcssim-api-dev.fresco.me
, and office365onboarding.fresco.me
is fresco.me
.
Four name servers, ns-158.awsdns-19.com
, ns-1020.awsdns-63.net
, ns-1146.awsdns-15.org
, and ns-1831.awsdns-36.co.uk
, are responsible for the delegation of fresco.me
.
The domain fresco.me
shares its name servers at least partially with other domains such as hotarugawa-clinic-toyama.com
, dycos.biz
, washingtonlawcenter.com
, b.lu
, and pdmp-apis.no
.
The name servers ns-661.awsdns-18.net
, ns-1217.awsdns-24.org
, ns-1991.awsdns-56.co.uk
, ns-1071.awsdns-05.org
, ns-905.awsdns-49.net
, ns-1923.awsdns-48.co.uk
, ns-408.awsdns-51.com
, ns-1977.awsdns-55.co.uk
, ns-1649.awsdns-14.co.uk
, and ns-1610.awsdns-09.co.uk
are often used in conjunction.
ns-158.awsdns-19.com
, 2600:9000:5300:9e00::1, and 205.251.192.158 are associated together.
ns-1020.awsdns-63.net
, 2600:9000:5303:fc00::1, and 205.251.195.252 are linked.
ns-1146.awsdns-15.org
, 2600:9000:5304:7a00::1, and 205.251.196.122 are connected.
ns-1831.awsdns-36.co.uk
, 2600:9000:5307:2700::1, and 205.251.199.39 are paired.
The mail server inbound-smtp.us-east-1.amazonaws.com
is responsible for handling fresco.me
.
Just like the domains gamedobem.com.br
, iraqroom.com
, app.homes.co.jp
, bp.enterprise.slack.com
, and agrotoulousains.slack.com
, fresco.me
also has the same mail server setup.
Some mail servers are shared, at least partially, by fresco.me
with other domains like uwufufu.com
, pchbtna.atlassian.net
, platon.atlassian.net
, it-enterprise.atlassian.net
, and alternativepower-solutions.com
.
The mail servers inbound-smtp.us-west-2.amazonaws.com
, aspmx.l.google.com
, alt1.aspmx.l.google.com
, alt2.aspmx.l.google.com
, alt3.aspmx.l.google.com
, and alt4.aspmx.l.google.com
are frequently utilized in conjunction.
inbound-smtp.us-east-1.amazonaws.com
points to the following five IP numbers: 3.211.210.226, 44.206.9.87, 44.210.166.32, 54.164.173.191, and 54.197.5.236.