yusercontent.com: IP address, DNS records and WHOIS
Live lookup data for yusercontent.com: the IP addresses it resolves to, the DNS records it publishes, and its registration details. The data below is fetched when this page is built and refreshed daily.
At a glance
DNS records
A
| 76.223.84.192 | TTL 86400 |
| 13.248.158.7 | TTL 86400 |
AAAA
No public records of this type are currently published.
CNAME
No public records of this type are currently published.
MX
| 0 |
NS
| blue.foundationdns.com |
| blue.foundationdns.net |
| blue.foundationdns.org |
| ns1.yahoo.com |
| ns2.yahoo.com |
| ns3.yahoo.com |
| ns4.yahoo.com |
| ns5.yahoo.com |
TXT
No public records of this type are currently published.
SOA
- Primary nameserver
- hidden-master.yahoo.com
- Hostmaster
- hostmaster@yahoo-inc.com
- Serial
- 2026102302
- Refresh
- 28800 s (8 hours)
- Retry
- 7200 s (2 hours)
- Expire
- 604800 s (7 days)
- Minimum TTL
- 86400 s (1 day)
CAA
| 0 iodef "mailto:security@yahooinc.com" |
| 0 issue "digicert.com" |
| 0 issue "globalsign.com" |
WHOIS registration data
- Registrar
- MarkMonitor Inc.
- Registered
- Nov 4, 2014
- Expires
- Nov 4, 2027
- Last changed
- Oct 3, 2026
- Status
- client delete prohibited, client transfer prohibited, client update prohibited
- Nameservers
- blue.foundationdns.com, blue.foundationdns.net, blue.foundationdns.org, ns1.yahoo.com, ns2.yahoo.com, ns3.yahoo.com, ns4.yahoo.com, ns5.yahoo.com
- DNSSEC signed
- No
FAQ
yusercontent.com currently resolves to 76.223.84.192, 13.248.158.7. Large sites often publish several addresses and rotate them, so the list can differ between checks and between locations.
yusercontent.com is registered through MarkMonitor Inc.. The registrant's identity is not published in the public registration record — most owners use a privacy service or the data is redacted.
yusercontent.com is served by blue.foundationdns.com, blue.foundationdns.net, blue.foundationdns.org, ns1.yahoo.com, ns2.yahoo.com, ns3.yahoo.com, ns4.yahoo.com, ns5.yahoo.com. These are the authoritative nameservers that publish its DNS records.
Run a fresh check
Records change. Run the live tools for an up-to-the-minute answer: