Hostname
smartosc.com
Last fetched
smartosc.com resolves to 104.26.8.15, announced in 104.26.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. smartosc.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.
Threat posture
0threat score (procedure-native scale)
NONENo threats observed.
- Threat feeds listing this
- 0
- Verdict coverage
- known-clean
Nutrition Label
Resolution chain
- 104.26.8.15
104.26.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 104.26.9.15
104.26.0.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
- 172.67.69.131
172.67.64.0/20 · CLOUDFLARENET - Cloudflare, Inc. · Toronto, CA
IPv6 resolution
Attribution
Cloudflare
cdn · ORIGIN_AS, CDN
WHOIS identity
- Registrar
- iana:146
- Registrant organisation
- domains by proxy,
- Contact emails
- rascator@smartosc.com, trungnh28@gmail.com
Subdomains
Web-graph footprint
Sampled `LINKS_TO` edges. The hyperlink layer is a pilot sample, not a web-scale crawl, so these are illustrative.
Sample inbound links
Mail and authentication
Nameservers
- elle.ns.cloudflare.com
- gabe.ns.cloudflare.com
- a.root-servers.net
- b.root-servers.net
- c.root-servers.net
- d.root-servers.net
- e.root-servers.net
- f.root-servers.net
- g.root-servers.net
- h.root-servers.net
- i.root-servers.net
- j.root-servers.net
- k.root-servers.net
- l.root-servers.net
- m.root-servers.net
MX records
- aspmx.l.google.com
- alt1.aspmx.l.google.com
- alt2.aspmx.l.google.com
- aspmx2.googlemail.com
- aspmx3.googlemail.com
SPF policy
- include: amazonses.com
- include: _spf.google.com
- include: sendersrv.com
- include: spf.sendinblue.com
- mx: smartosc.com
- include: mail.zohopeople.com
- ip: 113.161.61.110
- ip: 117.3.65.235
- ip: 117.6.178.182
- ip: 118.70.67.134
- ip: 128.199.231.120
- ip: 139.59.222.114
- ip: 139.59.238.113
- ip: 148.251.11.75
- ip: 178.128.114.27
- ip: 203.171.17.18
- ip: 210.245.35.101
- ip: 210.245.35.212
- ip: 222.252.27.56
- ip: 46.4.25.45
Threat-feed evidence
History
Related pages
Pivot from smartosc.com into the addresses, networks and registries it depends on.
Cypher and MCP
Reproduce this hostname's resolution chain against graph.whisper.security:
MATCH (h:HOSTNAME {name: "smartosc.com"})-[:RESOLVES_TO]->(ip:IPV4)
-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)-[:ROUTES]->(a:ASN)
OPTIONAL MATCH (a)-[:HAS_NAME]->(n:ASN_NAME)
RETURN ip.name AS ip, ap.name AS prefix, a.name AS asn, n.name AS network
LIMIT 20Or query Whisper from your own LLM workflow via the Whisper MCP server.