Skip to content

Hostname

lavishta.com

Last fetched

lavishta.com resolves to 104.26.0.174, announced in 104.26.0.0/20 by CLOUDFLARENET - Cloudflare, Inc. in CA. lavishta.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 · lavishta.comRouting diversity1.5/10Peering density10.0/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.0/10canon.whisper.security/host/lavishta.com

Resolution chain

IPv6 resolution

Attribution

Cloudflare

cdn · ORIGIN_AS, CDN

WHOIS identity

Registrar
iana:1068
Registrant organisation
domain admin
Contact emails
f36ecc4ab5ec4e8bb3693e34b76a1a7b.protect@whoisguard.com, 2972346610d24f4bbd8052900cb7ee94.protect@withheldforprivacy.com, lavishta.com-owner@customers.whoisprivacycorp.com

Subdomains

Subdomain
admin.lavishta.com
autodiscover.lavishta.com
c1e15676508f.lavishta.com
cpanel.lavishta.com
cpcalendars.lavishta.com
cpcontacts.lavishta.com
erp.lavishta.com
mail.lavishta.com
merged.lavishta.com
nafs.lavishta.com
preorder.lavishta.com
sadiqasif.lavishta.com

Showing 12 of 23. 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

Mail and authentication

Nameservers

  • nola.ns.cloudflare.com
  • quentin.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

  • _dc-mx.c1e15676508f.lavishta.com
  • mail.lavishta.com

SPF policy

  • include: _spf.google.com
  • include: _spf.mx.cloudflare.net

Threat-feed evidence

History

Related pages

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