fresco.me checked at 2025-02-26T21:10:38.519Z 208ms 105/105/105 100% R:15
DNS.NINJA - fresco.me
Search for IP or hostnames
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 |
AI analysis
fresco.me serves as the parent for play-api.fresco.me, play.fresco.me, tcssim-api-dev.fresco.me, and office365onboarding.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, have been delegated to fresco.me.
The domain fresco.me shares name servers, at least partially, with other domains such as hotarugawa-clinic-toyama.com, heygents.com.au, idcciosummit.com, clearimage.us, and d1ks79fq83zf4o.cloudfront.net.
The name servers ns-661.awsdns-18.net, ns-1217.awsdns-24.org, ns-1991.awsdns-56.co.uk, ns-376.awsdns-47.com, ns-1486.awsdns-57.org, ns-1821.awsdns-35.co.uk, ns-110.awsdns-13.com, ns-624.awsdns-14.net, ns-1835.awsdns-37.co.uk, and ns-905.awsdns-49.net are commonly used together.
ns-158.awsdns-19.com, ns-1020.awsdns-63.net, ns-1146.awsdns-15.org, and ns-1831.awsdns-36.co.uk all point to two IP numbers each: 2600:9000:5300:9e00::1 and 205.251.192.158; 2600:9000:5303:fc00::1 and 205.251.195.252; 2600:9000:5304:7a00::1 and 205.251.196.122; 2600:9000:5307:2700::1 and 205.251.199.39, respectively.
The mail server, inbound-smtp.us-east-1.amazonaws.com, handles fresco.me.
The mail server setup of fresco.me matches with other domains such as iraqroom.com, app.homes.co.jp, bp.enterprise.slack.com, cfa.slack.com, and nsesgroup.slack.com.
Other domains like uwufufu.com, pchbtna.atlassian.net, platon.atlassian.net, it-enterprise.atlassian.net, and alternativepower-solutions.com share some mail servers, at least partially, with fresco.me.
The mail servers inbound-smtp.us-west-2.amazonaws.com are commonly utilized in conjunction with these mail servers.
inbound-smtp.us-east-1.amazonaws.com is associated with five IP addresses: 3.211.210.226, 44.206.9.87, 44.210.166.32, 54.164.173.191, and 54.197.5.236.