Skip to content

Hostname

urbanic.com

Last fetched

urbanic.com resolves to 108.158.213.102, announced in 108.159.42.0/24 by AMAZON-02 - Amazon.com, Inc. in SG. urbanic.com is not listed on any threat feed indexed by WhisperGraph; reconciled level NONE.

Threat posture

0threat score (procedure-native scale)

NONE

No threats observed.

Threat feeds listing this
0
Verdict coverage
known-clean

Nutrition Label

WHISPER CANON · urbanic.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/urbanic.com

Resolution chain

IPv6 resolution

No AAAA record for urbanic.com is recorded in WhisperGraph.

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:1659
Registrant organisation
domains by proxy,
Contact emails
384980@privacy-link.com, dbp@domainsbyproxy.com, pkrastogi59@gmail.com

Subdomains

Subdomain
api-shop-br.urbanic.com
api-shop-in.urbanic.com
api-shop-mx.urbanic.com
api-shop-us.urbanic.com
base.urbanic.com
br.urbanic.com
buyer-file-br.urbanic.com
buyer-file-in.urbanic.com
buyer-file-mx.urbanic.com
buyer-img-in.urbanic.com
buyer-img-mx.urbanic.com
buyer-material-br.urbanic.com

Showing 12 of 58. View all 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

Sample outbound links

Mail and authentication

Nameservers

  • ns-264.awsdns-33.com
  • ns-844.awsdns-41.net
  • ns-1306.awsdns-35.org
  • ns-1861.awsdns-40.co.uk

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • alt3.aspmx.l.google.com
  • alt4.aspmx.l.google.com

SPF policy

  • include: _spf.google.com

Threat-feed evidence

History

Related pages

Pivot from urbanic.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: "urbanic.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 20

Or query Whisper from your own LLM workflow via the Whisper MCP server.