Skip to content

Hostname

ubiregi.com

Last fetched

ubiregi.com resolves to 108.157.142.115, announced in 108.157.136.0/21 by AMAZON-02 - Amazon.com, Inc. in US. ubiregi.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 · ubiregi.comRouting diversity1.5/10Peering density9.7/10MOAS conflict✓ noneThreat-feed listings10.0/10WHOIS transparency10.0/10Resolver footprint4.6/10canon.whisper.security/host/ubiregi.com

Resolution chain

IPv6 resolution

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

Attribution

Aws

cloud · ORIGIN_AS

WHOIS identity

Registrar
iana:48
Registrant organisation
soutaro matsumoto
Contact emails
dev@ubiregi.com

Subdomains

Subdomain
api-doc.ubiregi.com
app.ubiregi.com
assets.ubiregi.com
basecamp.ubiregi.com
blog.ubiregi.com
choushimarusandbox.ubiregi.com
com.ubiregi.com
corp.ubiregi.com
fqr.ubiregi.com
go.ubiregi.com
handy.ubiregi.com
load-test-app.ubiregi.com

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

  • ns1.dnsimple.com
  • ns2.dnsimple.com
  • ns3.dnsimple.com
  • ns4.dnsimple.com

MX records

  • aspmx.l.google.com
  • alt1.aspmx.l.google.com
  • alt2.aspmx.l.google.com
  • aspmx2.l.google.com
  • aspmx3.googlemail.com
  • aspmx4.googlemail.com
  • aspmx5.googlemail.com

SPF policy

  • ip: 136.143.184.0/24
  • ip: 136.143.188.0/24
  • ip: 199.67.64.0/24
  • ip: 135.84.80.0/24
  • ip: 135.84.82.0/24
  • ip: 117.20.43.11/32
  • include: _spf.google.com
  • include: et._spf.pardot.com
  • include: _spf.salesforce.com
  • include: _spf.activegate-ss.jp
  • include: sendgrid.net

Threat-feed evidence

History

Related pages

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