domains Seems that Google has acquired the domain hack Near(.)by

[domainnews]

Last year ， I found there was no any
updated infos of this domain，but today I found the who is has changed seems that google has bought it from the market.

Howere， What amounts of this domain shall be still in the air.

BTW，another domain hack Simil.ar sold for 22000USD at Sedo recently

 

[Future Sensors]

It's a nice domain hack, but this domain wasn't acquired recently.

For instance, a TLS cert active at 2019-09-02 already included the NEAR.BY domain, together with a LOT of other Google related domains.

Although Google didn't widely advertise a public "Nearby" consumer site in 2019, they were already preparing infrastructure for their:

• Nearby Share APIs (used in Android for peer-to-peer transfers)
• "Fast Pair" Bluetooth device discovery
• Background proximity services in Google Play Services

By including *.near.by in the SAN list, Google ensured any future subdomain (for example api.near.by or connect.near.by) would immediately have a valid certificate.

Version: V3
Serial Number: c0185ecb391de3f7080000000011bb3d
Thumbprint: 27a3196e589b5f384132321f710a5f49465adc3c
Signature Algorithm: sha256RSA
Issuer: C=US CN=GTS CA 1O1 O=Google Trust Services
Validity
Not Before: 2019-08-23 10:27:10
Not After: 2019-11-21 10:27:10
Subject: C=US ST=California L=Mountain View O=Google LLC CN=misc.google.com

[..]

X509v3 Subject Alternative Name:

[..]

DNS:*.near.by,

 

[domainnews]

It's a nice domain hack, but this domain wasn't acquired recently.

For instance, a TLS cert from 2019-09-02 already included the NEAR.BY domain, together with a LOT of other Google related domains.

Although Google didn't widely advertise a public "Nearby" consumer site in 2019, they were already preparing infrastructure for their:

• Nearby Share APIs (used in Android for peer-to-peer transfers)
• "Fast Pair" Bluetooth device discovery
• Background proximity services in Google Play Services

By including *.near.by in the SAN list, Google ensured any future subdomain (for example api.near.by or connect.near.by) would immediately have a valid certificate.

Version: V3
Serial Number: c0185ecb391de3f7080000000011bb3d
Thumbprint: 27a3196e589b5f384132321f710a5f49465adc3c
Signature Algorithm: sha256RSA
Issuer: C=US CN=GTS CA 1O1 O=Google Trust Services
Validity
Not Before: 2019-08-23 10:27:10
Not After: 2019-11-21 10:27:10
Subject: C=US ST=California L=Mountain View O=Google LLC CN=misc.google.com

[...]

X509v3 Subject Alternative Name:

[..]

DNS:*.near.by,

This domain is owned by an American before， the whois info had not been changed to Google as I checked last year，maybe，acquired by Google at the end of last year.

A director of tech of Google inquired
about one of my Domain Hacks this Year but the priced High and scared him runned away

 

[Future Sensors]

acquired by Google at the end of last year

I don't think that's the case (not recently).

 

[domainnews]

I don't think that's the case (not recently).

This domain acquired by google 97% percent because the DNS not Google before the end of last year

 

[Catch.Center]

What project will it be used to?

 

[Future Sensors]

What project will it be used to?

https://developers.google.com/nearby/