Skip to content

Hostname

lamayor.org

Last fetched

lamayor.org resolves to 23.205.106.82, announced in 23.205.106.0/24 by AKAMAI-ASN1 - Akamai International B.V. in US. lamayor.org 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 · lamayor.orgRouting diversity1.5/10Peering density9.3/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint8.6/10canon.whisper.security/host/lamayor.org

Resolution chain

IPv6 resolution

No AAAA record for lamayor.org is recorded in WhisperGraph.

Attribution

akamai international

ORIGIN_AS

WHOIS identity

Registrar
iana:2
Registrant organisation
city of los angeles - ita
Contact emails
balmore.botero@lacity.org, madeline.paguio@lacity.org

Subdomains

Subdomain
coronavirus.lamayor.org
jobs.lamayor.org
plan.lamayor.org
plans.lamayor.org
sdg.lamayor.org
sdgdata.lamayor.org
sdgdatabase.lamayor.org
volunteer.lamayor.org
www.lamayor.org

Showing 9 of 11. 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

  • ns10.digicertdns.com
  • ns0.dnsmadeeasy.com
  • ns1.dnsmadeeasy.com
  • ns2.dnsmadeeasy.com
  • ns3.dnsmadeeasy.com
  • ns4.dnsmadeeasy.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

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

Threat-feed evidence

History

Related pages

Pivot from lamayor.org 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: "lamayor.org"})-[: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.